SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

</head>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">For the defense fair, see <a href="International_Defence_Industry_Fair" title="International Defence Industry Fair">International Defence Industry Fair</a>.</div>

<p><b>IDEF</b>, initially an abbreviation of <b>ICAM Definition</b> and renamed in 1999 as <b>Integration Definition</b>, is a family of modeling languages in the field of systems and software engineering. They cover a wide range of uses from functional modeling to data, simulation, <a href="Object-oriented_analysis_and_design" title="Object-oriented analysis and design">object-oriented analysis and design</a>, and knowledge acquisition. These definition languages were developed under funding from U.S. Air Force and, although still most commonly used by them and other military and United States Department of Defense (DoD) agencies, are in the public domain.

</p><p>The most-widely recognized and used components of the IDEF family are IDEF0, a functional modeling language building on SADT, and IDEF1X, which addresses information models and database design issues.

</p>

<div class="mw-heading mw-heading2"><h2 id="Overview_of_IDEF_methods">Overview of IDEF methods</h2></div>

<p>IDEF refers to a family of <a href="Modeling_language" title="Modeling language">modeling language</a>, which cover a wide range of uses, from functional modeling to data, simulation, object-oriented analysis/design and knowledge acquisition. Eventually the IDEF methods have been defined up to IDEF14:

</p>

<ul><li><a href="IDEF0" title="IDEF0">IDEF0</a>: Function modeling<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup></li>

<li><a href="IDEF1X#History" title="IDEF1X">IDEF1</a>: Information modeling<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup></li>

<li><a href="IDEF1X" title="IDEF1X">IDEF1X</a>: Data modeling<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup></li>

<li><a href="IDEF2" class="mw-redirect" title="IDEF2">IDEF2</a>: Simulation model design</li>

<li><a href="IDEF3" title="IDEF3">IDEF3</a>: Process description capture<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup></li>

<li><a href="IDEF4" title="IDEF4">IDEF4</a>: Object-oriented design<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup></li>

<li><a href="IDEF5" title="IDEF5">IDEF5</a>: Ontology description capture<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup></li>

<li><a href="IDEF6" title="IDEF6">IDEF6</a>: Design rationale capture<sup id="cite_ref-MGM90_7-0" class="reference"><a href="#cite_note-MGM90-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup></li>

<li>IDEF7: Information system auditing</li>

<li>IDEF8: User interface modeling</li>

<li>IDEF9: Business constraint discovery</li>

<li>IDEF10: Implementation architecture modeling</li>

<li>IDEF11: Information artifact modeling</li>

<li>IDEF12: Organization modeling</li>

<li>IDEF13: Three-schema mapping design</li>

<li>IDEF14: Network design</li></ul>

<p>In 1995 only the <a href="IDEF0" title="IDEF0">IDEF0</a>, <a href="IDEF1X" title="IDEF1X">IDEF1X</a>, <a href="IDEF2" class="mw-redirect" title="IDEF2">IDEF2</a>, <a href="IDEF3" title="IDEF3">IDEF3</a> and <a href="IDEF4" title="IDEF4">IDEF4</a> had been developed in full.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> Some of the other IDEF concepts had some preliminary design. Some of the last efforts were new IDEF developments in 1995 toward establishing reliable methods for business constraint discovery IDEF9, design rationale capture <a href="IDEF6" title="IDEF6">IDEF6</a>, human system, interaction design IDEF8, and network design IDEF14.<sup id="cite_ref-May05_9-0" class="reference"><a href="#cite_note-May05-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p><p>The methods IDEF7, IDEF10, IDEF11, IDEF 12 and IDEF13 haven't been developed any further than their initial definition.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>IDEF originally stood for <a href="Integrated_Computer-Aided_Manufacturing" title="Integrated Computer-Aided Manufacturing">ICAM</a> Definition, initiated in the 1970s at the US Air Force Materials Laboratory, <a href="Wright-Patterson_Air_Force_Base" title="Wright-Patterson Air Force Base">Wright-Patterson Air Force Base</a> in Ohio by <a href="Dennis_E._Wisnosky" title="Dennis E. Wisnosky">Dennis E. Wisnosky</a>, Dan L. Shunk, and others.<sup id="cite_ref-Sav96_11-0" class="reference"><a href="#cite_note-Sav96-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> and completed in the 1980s. IDEF was a product of the ICAM initiative of the <a href="United_States_Air_Force" title="United States Air Force">United States Air Force</a>. The <a href="Institute_of_Electrical_and_Electronics_Engineers" title="Institute of Electrical and Electronics Engineers">IEEE</a> recast the IDEF abbreviation as Integration Definition."<sup id="cite_ref-IEEE_IDEF_Ref_12-0" class="reference"><a href="#cite_note-IEEE_IDEF_Ref-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p><p>The specific projects that produced IDEF were ICAM project priorities 111 and 112 (later renumbered 1102). The subsequent Integrated Information Support System (IISS) project priorities 6201, 6202, and 6203 attempted to create an <a href="Data_processing" title="Data processing">information processing</a> environment that could be run in <a href="Heterogeneous" class="mw-redirect" title="Heterogeneous">heterogeneous</a> physical computing environments. Further development of IDEF occurred under those projects as a result of the experience gained from applications of the new modeling techniques. The intent of the IISS efforts was to create 'generic subsystems' that could be used by a large number of collaborating enterprises, such as U.S. <a href="Defense_contractor" class="mw-redirect" title="Defense contractor">defense contractors</a> and the armed forces of friendly nations.

</p><p>At the time of the ICAM 1102 effort there were numerous, mostly incompatible, <a href="Data_model" title="Data model">data model</a> methods for storing computer data — <a href="Sequential_access" title="Sequential access">sequential</a> (<a href="VSAM" class="mw-redirect" title="VSAM">VSAM</a>), <a href="Hierarchical_model" class="mw-redirect" title="Hierarchical model">hierarchical</a> (<a href="Information_Management_System" class="mw-redirect" title="Information Management System">IMS</a>), <a href="Network_model" title="Network model">network</a> (<a href="Cincom" class="mw-redirect" title="Cincom">Cincom</a>'s TOTAL and <a href="CODASYL" title="CODASYL">CODASYL</a>, and <a href="Cullinet" title="Cullinet">Cullinet</a>'s <a href="IDMS" title="IDMS">IDMS</a>). The <a href="Relational_data_model" class="mw-redirect" title="Relational data model">relational data model</a> was just emerging as a promising way of thinking about structuring data for easy, efficient, and accurate access. <a href="Relational_database_management_system" class="mw-redirect" title="Relational database management system">Relational database management systems</a> had not yet emerged as a general standard for data management.

</p><p>The ICAM program office deemed it valuable to create a "neutral" way of describing the data content of large-scale systems. The emerging academic literature suggested that methods were needed to process <a href="Data_independence" title="Data independence">data independently</a> of the way it was <a href="Data_structure" title="Data structure">physically stored</a>. Thus the IDEF1 language was created to allow a neutral description of data structures that could be applied regardless of the storage method or file access method.

</p><p>IDEF1 was developed under ICAM program priority 1102 by Robert R. Brown of the <a href="Hughes_Aircraft_Company" title="Hughes Aircraft Company">Hughes Aircraft Company</a>, under contract to <a href="SofTech%2C_Inc." class="mw-redirect" title="SofTech, Inc.">SofTech, Inc.</a> Brown had previously been responsible for the development of <a href="Information_Management_System" class="mw-redirect" title="Information Management System">IMS</a> while working at <a href="Rockwell_International" title="Rockwell International">Rockwell International</a>. Rockwell chose not to pursue IMS as a marketable product but <a href="International_Business_Machines" class="mw-redirect" title="International Business Machines">IBM</a>, which had served as a support contractor during development, subsequently took over the product and was successful in further developing it for market. Brown credits his Hughes colleague Timothy Ramey as the inventor of IDEF1 as a viable formalism for modeling information structures. The two Hughes researchers built on ideas from and interactions with many luminaries in the field at the time. In particular, IDEF1 draws on the following techniques:

</p>

<ul><li>the evolving natural language information model (<a href="NIAM" class="mw-redirect" title="NIAM">ENALIM</a>) technique of <a href="G._M._Nijssen" title="G. M. Nijssen">G. M. Nijssen</a> (<a href="Control_Data_Corporation" title="Control Data Corporation">Control Data Corporation</a>) — this technique is now more widely known as <a href="NIAM" class="mw-redirect" title="NIAM">NIAM</a> or the object–role model <a href="Object%E2%80%93role_modeling" title="Object–role modeling">ORM</a>;</li>

<li>the network data structures technique, popularly called the <a href="CODASYL" title="CODASYL">CODASYL</a> approach, of <a href="Charles_Bachman" title="Charles Bachman">Charles Bachman</a> (<a href="Honeywell_Information_Systems" class="mw-redirect" title="Honeywell Information Systems">Honeywell Information Systems</a>);</li>

<li>the hierarchical data management technique, implemented in IBM's IMS data management system, developed by <a href="R._R._Brown" title="R. R. Brown">R. R. Brown</a> (<a href="Rockwell_International" title="Rockwell International">Rockwell International</a>);</li>

<li>the relational approach to data of <a href="E._F._Codd" class="mw-redirect" title="E. F. Codd">E. F. Codd</a> (<a href="IBM" title="IBM">IBM</a>);</li>

<li>The <a href="Entity%E2%80%93relationship_model" title="Entity–relationship model">entity–relationship approach</a> (E–R) of <a href="Peter_Chen" title="Peter Chen">Peter Chen</a> (<a href="UCLA" class="mw-redirect" title="UCLA">UCLA</a>).</li></ul>

<p>The effort to develop IDEF1 resulted in both a new method for information modeling and an example of its use in the form of a "reference information model of manufacturing." This latter artifact was developed by D. S. Coleman of the D. Appleton Company (DACOM) acting as a sub-contractor to Hughes and under the direction of Ramey. Personnel at DACOM became expert at IDEF1 modeling and subsequently produced a training course and accompanying materials for the IDEF1 modeling technique.

</p><p>Experience with IDEF1 revealed that the translation of information requirements into database designs was more difficult than had originally been anticipated. The most beneficial value of the IDEF1 information modeling technique was its ability to represent data independent of how those data were to be stored and used. It provided data modelers and data analysts with a way to represent data requirements during the requirements-gathering process. This allowed designers to decide which DBMS to use after the nature of the data requirements was understood and thus reduced the "misfit" between data requirements and the capabilities and limitations of the DBMS. The translation of IDEF1 models to database designs, however, proved to be difficult.

</p>

<div class="mw-heading mw-heading2"><h2 id="The_IDEF_modeling_languages">The IDEF modeling languages</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="IDEF0" title="IDEF0">IDEF0</a></div>

<p>The IDEF0 functional modeling method is designed to model the decisions, actions, and activities of an organization or system.<sup id="cite_ref-VG00_13-0" class="reference"><a href="#cite_note-VG00-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> It was derived from the established graphic modeling language <a href="Structured_Analysis_and_Design_Technique" class="mw-redirect" title="Structured Analysis and Design Technique">structured analysis and design technique</a> (SADT) developed by <a href="Douglas_T._Ross" title="Douglas T. Ross">Douglas T. Ross</a> and <a href="SofTech%2C_Inc." class="mw-redirect" title="SofTech, Inc.">SofTech, Inc.</a> In its original form, IDEF0 includes both a definition of a graphical modeling language (<a href="Syntax" title="Syntax">syntax</a> and <a href="Semantics" title="Semantics">semantics</a>) and a description of a comprehensive methodology for developing models.<sup id="cite_ref-ITL93_14-0" class="reference"><a href="#cite_note-ITL93-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> The US Air Force commissioned the SADT developers to develop a <a href="Function_model" title="Function model">function model</a> method for analyzing and communicating the functional perspective of a system. IDEF0 should assist in organizing system analysis and promote effective communication between the analyst and the customer through simplified graphical devices.<sup id="cite_ref-VG00_13-1" class="reference"><a href="#cite_note-VG00-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup>

</p>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="IDEF1X" title="IDEF1X">IDEF1X</a></div>

<p>To satisfy the <a href="Data_modeling" title="Data modeling">data modeling</a> enhancement requirements that were identified in the IISS-6202 project, a sub-contractor, DACOM, obtained a license to the <a href="Logical_database_design_technique" class="mw-redirect" title="Logical database design technique">logical database design technique</a> (LDDT) and its supporting software (ADAM). LDDT had been developed in 1982 by Robert G. Brown of The Database Design Group entirely outside the IDEF program and with no knowledge of IDEF1. LDDT combined elements of the relational data model, the E–R model, and generalization in a way specifically intended to support data modeling and the transformation of the data models into database designs. The graphic syntax of LDDT differed from that of IDEF1 and, more importantly, LDDT contained interrelated modeling concepts not present in IDEF1. Mary E. Loomis wrote a concise summary of the syntax and semantics of a substantial subset of LDDT, using terminology compatible with IDEF1 wherever possible. DACOM labeled the result <a href="IDEF1X" title="IDEF1X">IDEF1X</a> and supplied it to the ICAM program.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup>

</p><p>Because the IDEF program was funded by the government, the techniques are in the <a href="Public_domain" title="Public domain">public domain</a>. In addition to the ADAM software, sold by DACOM under the name Leverage, a number of <a href="Computer-aided_software_engineering" title="Computer-aided software engineering">CASE</a> tools use <a href="IDEF1X" title="IDEF1X">IDEF1X</a> as their representation technique for data modeling.

</p><p>The IISS projects actually produced working prototypes of an information processing environment that would run in heterogeneous computing environments. Current advancements in such techniques as <a href="Java_(programming_language)" title="Java (programming language)">Java</a> and <a href="JDBC" class="mw-redirect" title="JDBC">JDBC</a> are now achieving the goals of ubiquity and versatility across computing environments which was first demonstrated by IISS.

</p>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="IDEF3" title="IDEF3">IDEF3</a></div>

<p>The third IDEF (IDEF2) was originally intended as a user interface modeling method. However, since the <a href="Integrated_Computer-Aided_Manufacturing" title="Integrated Computer-Aided Manufacturing">Integrated Computer-Aided Manufacturing</a> (ICAM) program needed a simulation modeling tool, the resulting IDEF2 was a method for representing the time varying behavior of resources in a manufacturing system, providing a framework for specification of math model based simulations. It was the intent of the methodology program within <a href="Integrated_Computer-Aided_Manufacturing" title="Integrated Computer-Aided Manufacturing">ICAM</a> to rectify this situation but limitation of funding did not allow this to happen. As a result, the lack of a method which would support the structuring of descriptions of the user view of a system has been a major shortcoming of the IDEF system. The basic problem from a methodology point of view is the need to distinguish between a description of what a system (existing or proposed) is supposed to do and a representative simulation model that predicts what a system will do. The latter was the focus of <a href="IDEF2" class="mw-redirect" title="IDEF2">IDEF2</a>, the former is the focus of <a href="IDEF3" title="IDEF3">IDEF3</a>.<sup id="cite_ref-FB89_17-0" class="reference"><a href="#cite_note-FB89-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup>

</p>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="IDEF4" title="IDEF4">IDEF4</a></div>

<p>The development of <a href="IDEF4" title="IDEF4">IDEF4</a> came from the recognition that the modularity, maintainability and code reusability that results from the <a href="Object-oriented_programming" title="Object-oriented programming">object-oriented programming</a> paradigm can be realized in traditional <a href="Data_processing" title="Data processing">data processing</a> applications. The proven ability of the object-oriented programming paradigm to support data level integration in large complex <a href="Distributed_system" class="mw-redirect" title="Distributed system">distributed systems</a> is also a major factor in the widespread interest in this technology from the traditional data processing community.<sup id="cite_ref-FB89_17-1" class="reference"><a href="#cite_note-FB89-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup>

</p><p><a href="IDEF4" title="IDEF4">IDEF4</a> was developed as a design tool for software designers who use object-oriented languages such as the <a href="Common_Lisp_Object_System" title="Common Lisp Object System">Common Lisp Object System</a>, <a href="Flavors_(programming_language)" title="Flavors (programming language)">Flavors</a>, <a href="Smalltalk" title="Smalltalk">Smalltalk</a>, <a href="Objective-C" title="Objective-C">Objective-C</a>, <a href="C%2B%2B" title="C++">C++</a>, and others. Since effective usage of the object-oriented paradigm requires a different thought process than used with conventional procedural or <a href="Database_language" class="mw-redirect" title="Database language">database languages</a>, standard methodologies such as <a href="Structure_chart" title="Structure chart">structure charts</a>, <a href="Data_flow_diagram" class="mw-redirect" title="Data flow diagram">data flow diagrams</a>, and traditional <a href="Database_model" title="Database model">data design models</a> (hierarchical, relational, and network) are not sufficient. IDEF4 seeks to provide the necessary facilities to support the object-oriented design decision making process.<sup id="cite_ref-FB89_17-2" class="reference"><a href="#cite_note-FB89-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup>

</p>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="IDEF5" title="IDEF5">IDEF5</a></div>

<p><a href="IDEF5" title="IDEF5">IDEF5</a>, or integrated definition for ontology description capture method, is a software engineering method to develop and maintain usable, accurate, domain <a href="Ontology_(computer_science)" class="mw-redirect" title="Ontology (computer science)">ontologies</a>.<sup id="cite_ref-PCB94_18-0" class="reference"><a href="#cite_note-PCB94-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup> In the field of computer science ontologies are used to capture the <a href="Concept_and_object" title="Concept and object">concept and objects</a> in a specific <a href="Domain_analysis" title="Domain analysis">domain</a>, along with associated relationships and meanings. In addition, ontology capture helps coordinate projects by standardizing <a href="Terminology" title="Terminology">terminology</a> and creates opportunities for <a href="Information" title="Information">information</a> reuse. The IDEF5 Ontology Capture Method has been developed to reliably construct ontologies in a way that closely reflects human <a href="Understanding" title="Understanding">understanding</a> of the specific domain.<sup id="cite_ref-PCB94_18-1" class="reference"><a href="#cite_note-PCB94-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup>

</p><p>In the IDEF5 method, an ontology is constructed by capturing the content of certain assertions about real-world objects, their properties and their interrelationships, and representing that content in an intuitive and natural form. The IDEF5 method has three main components: A graphical language to support conceptual ontology analysis, a structured text language for detailed ontology characterization, and a systematic procedure that provides guidelines for effective ontology capture.<sup id="cite_ref-autogenerated1_19-0" class="reference"><a href="#cite_note-autogenerated1-19"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup>

</p>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="IDEF6" title="IDEF6">IDEF6</a></div>

<p><a href="IDEF6" title="IDEF6">IDEF6</a>, or integrated definition for design rationale capture, is a method to facilitate the acquisition, representation, and manipulation of the <a href="Design_rationale" title="Design rationale">design rationale</a> used in the development of <a href="Enterprise_systems" class="mw-redirect" title="Enterprise systems">enterprise systems</a>. Rationale is the reason, justification, underlying motivation, or excuse that moved the designer to select a particular strategy or design feature. More simply, rationale is interpreted as the answer to the question, “Why is this design being done in this manner?” Most design methods focus on what the design is (i.e. on the final product, rather than why the design is the way it is).<sup id="cite_ref-May05_9-1" class="reference"><a href="#cite_note-May05-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p><p>IDEF6 is a method that possesses the conceptual resources and linguistic capabilities needed

</p>

<ol><li>to represent the nature and structure of the information that constitutes design rationale within a given system, and</li>

<li>to associate that rationale with design specifications, models, and documentation for the system.</li></ol>

<p>IDEF6 is applicable to all phases of the information system development process, from initial conceptualization through both preliminary and detailed design activities. To the extent that detailed design decisions for software systems are relegated to the coding phase, the IDEF6 technique should be usable during the software construction process as well.<sup id="cite_ref-MGM90_7-1" class="reference"><a href="#cite_note-MGM90-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p>

<p>IDEF8, or integrated definition for human-system interaction design, is a method for producing high-quality designs of interactions between users and the systems they operate. Systems are characterized as a collection of objects that perform functions to accomplish a particular goal. The system with which the user interacts can be any system, not necessarily a computer program. Human-system interactions are designed at three levels of specification within the IDEF8 method. The first level defines the philosophy of system operation and produces a set of models and textual descriptions of overall system processes. The second level of design specifies role-centered scenarios of system use. The third level of IDEF8 design is for human-system design detailing. At this level of design, IDEF8 provides a library of metaphors to help users and designers specify the desired behavior in terms of other objects whose behavior is more familiar. Metaphors provide a model of abstract concepts in terms of familiar, concrete objects and experiences.<sup id="cite_ref-May05_9-2" class="reference"><a href="#cite_note-May05-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p>

<p>IDEF9, or integrated definition for business constraint discovery, is designed to assist in the discovery and analysis of constraints in a <a href="Business_system" class="mw-redirect" title="Business system">business system</a>. A primary motivation driving the development of IDEF9 was an acknowledgment that the collection of constraints that forge an enterprise system is generally poorly defined. The knowledge of what constraints exist and how those constraints interact is incomplete, disjoint, distributed, and often completely unknown. Just as living organisms do not need to be aware of the genetic or autonomous constraints that govern certain behaviors, organizations can (and most do) perform well without explicit knowledge of the glue that structures the system. In order to modify business in a predictable manner, however, the knowledge of these constraints is as critical as knowledge of genetics is to the genetic engineer.<sup id="cite_ref-May05_9-3" class="reference"><a href="#cite_note-May05-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p>

<p>IDEF14, or integrated definition for network design method, is a method that targets the modeling and design of <a href="Computer_network" title="Computer network">computer</a> and <a href="Communication_network" class="mw-redirect" title="Communication network">communication networks</a>. It can be used to model existing ("as is") or envisioned ("to be") networks. It helps the network designer to investigate potential network designs and to document design rationale. The fundamental goals of the IDEF14 research project developed from a perceived need for good network designs that can be implemented quickly and accurately.<sup id="cite_ref-May05_9-4" class="reference"><a href="#cite_note-May05-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

<p><span class="noviewer" typeof="mw:File"><span></span></span> This article incorporates <a href="Copyright_status_of_works_by_the_federal_government_of_the_United_States" title="Copyright status of works by the federal government of the United States">public domain material</a> from the <a rel="nofollow" class="external text" href="https://www.nist.gov">National Institute of Standards and Technology</a>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.idef.com/IDEF0.htm">IDEFØ Overview</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160305001934/http://www.idef.com/IDEF0.htm">Archived</a> 2016-03-05 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at idef.com</span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.idef.com/IDEF1.htm">IDEF1 Overview</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160303225827/http://www.idef.com/IDEF1.htm">Archived</a> 2016-03-03 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at idef.com</span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.idef.com/IDEF1x.htm">IDEF1x Overview</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160308075846/http://www.idef.com/idef1X.htm">Archived</a> 2016-03-08 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at idef.com</span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.idef.com/IDEF3.htm">IDEF3 Overview</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20100425012200/http://www.idef.com/IDEF3.htm">Archived</a> 2010-04-25 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at idef.com</span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.idef.com/IDEF4.htm">IDEF4 Overview</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160227141819/http://www.idef.com/IDEF4.htm">Archived</a> 2016-02-27 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at idef.com</span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.idef.com/IDEF5.htm">IDEF5 Overview</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160303225811/http://www.idef.com/IDEF5.htm">Archived</a> 2016-03-03 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> at idef.com</span>

</li>

<li id="cite_note-MGM90-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-MGM90_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-MGM90_7-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="Richard_J._Mayer" title="Richard J. Mayer">Mayer, Richard J.</a>; Griffith, Patricia A.; Menzel, Christopher P. (1990-91) <a rel="nofollow" class="external text" href="http://stinet.dtic.mil/oai/oai?&verb=getRecord&metadataPrefix=html&identifier=ADA261594">"IDEF6: A Design Rationale Capture Method Concept Paper"</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070402035120/http://stinet.dtic.mil/oai/oai?&verb=getRecord&metadataPrefix=html&identifier=ADA261594">Archived</a> 2007-04-02 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> Defense Technical Information Center</span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text">Robert P. Hanrahan <a rel="nofollow" class="external text" href="http://www.stsc.hill.af.mil/crosstalk/1995/06/IDEF.asp">The IDEF Process Modeling Methodology</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070126094915/http://www.stsc.hill.af.mil/crosstalk/1995/06/IDEF.asp">Archived</a> 2007-01-26 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. Software Technology Support Center. 1995</span>

</li>

<li id="cite_note-May05-9"><span class="mw-cite-backlink">^ <a href="#cite_ref-May05_9-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-May05_9-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-May05_9-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-May05_9-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-May05_9-4"><sup><i><b>e</b></i></sup></a></span> <span class="reference-text"><a href="Richard_J._Mayer" title="Richard J. Mayer">Richard J. Mayer</a> (1995) et al. <a rel="nofollow" class="external text" href="http://www.idef.com/pdf/compendium.pdf">Information Integration for Concurrent Engineering (IICE) Compendium of methods report</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20070711223834/http://www.idef.com/pdf/compendium.pdf">Archived</a> 2007-07-11 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. Wright-Patterson Air Force Base, Ohio 45433-7604.</span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://it.toolbox.com/blogs/enterprise-solutions/idef-standards-overview-18730">Observations from a Tech Architect: Enterprise Implementation Issues & Solutions</a> Craig Borysowich. Accessed 20 Jan 2009.</span>

</li>

<li id="cite_note-Sav96-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-Sav96_11-0">^</a></b></span> <span class="reference-text">Charles M. Savage (1996). <i>Fifth Generation Management: Co-creating Through Virtual Enterprising, Dynamic Teaming, and Knowledge Networking</i> Butterworth-Heinemann, 1996. <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-7506-9701-6</bdi>. p. 184.</span>

</li>

<li id="cite_note-IEEE_IDEF_Ref-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-IEEE_IDEF_Ref_12-0">^</a></b></span> <span class="reference-text">IEEE Standard for Functional Modeling Language—Syntax and Semantics for IDEF0, Software Engineering Standards Committee of the IEEE Computer Society, IEEE-SA Standards Board, The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA, <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130509181157/http://standards.ieee.org/findstds/standard/1320.1-1998.html">IEEE Std 1320.1-1998</a>, 25 June 1998</span>

</li>

<li id="cite_note-VG00-13"><span class="mw-cite-backlink">^ <a href="#cite_ref-VG00_13-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-VG00_13-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Varun Grover, William J. Kettinger (2000). <i>Process Think: Winning Perspectives for Business Change in the Information Age</i>. p. 168.</span>

</li>

<li id="cite_note-ITL93-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-ITL93_14-0">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.itl.nist.gov/fipspubs/idef02.doc">FIPS Publication 183</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20090227122140/http://www.itl.nist.gov/fipspubs/idef02.doc">Archived</a> 2009-02-27 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> released of IDEFØ December 1993 by the Computer Systems Laboratory of the National Institute of Standards and Technology (NIST).</span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text">IEEE (1998). <i>IEEE Std 1320.2-1998. IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X</i>. New York. p. iii.</span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text">Bruce, Thomas A. (1992), Designing Quality Databases with IDEF1X Information Models, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-932633-18-8</bdi> p=xii</span>

</li>

<li id="cite_note-FB89-17"><span class="mw-cite-backlink">^ <a href="#cite_ref-FB89_17-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-FB89_17-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-FB89_17-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text">Patricia Griffith Friel and Thomas M. Blinn (1989). <a rel="nofollow" class="external text" href="https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19910023489_1991023489.pdf">"Automated IDEF3 and IDEF4 Systems Design Specification Document"</a>. Technical report. NASA Johnson Space Center.</span>

</li>

<li id="cite_note-PCB94-18"><span class="mw-cite-backlink">^ <a href="#cite_ref-PCB94_18-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-PCB94_18-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Perakath C. Benjamin et al. (1994). <a rel="nofollow" class="external text" href="http://www.idef.com/pdf/Idef5.pdf"><i>IDEF5 Method Report</i></a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20081221091108/http://www.idef.com/pdf/Idef5.pdf">Archived</a> 2008-12-21 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>. Knowledge Based Systems, Inc.</span>

</li>

<li id="cite_note-autogenerated1-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-autogenerated1_19-0">^</a></b></span> <span class="reference-text">Varun Grover, William J. Kettinger (2000). <i>Process Think: Winning Perspectives for Business Change in the Information Age</i>. p.176-178</span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li>Ovidiu S. Noran (2000). <a rel="nofollow" class="external text" href="http://www.cit.gu.edu.au/~noran/Docs/UMLvsIDEF.pdf">Business Modelling: UML vs. IDEF</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20060113085843/http://www.cit.gu.edu.au/~noran/Docs/UMLvsIDEF.pdf">Archived</a> 2006-01-13 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a> Paper Griffith University</li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <span style="font-weight: bold; font-style: italic;"><a href="https://commons.wikimedia.org/wiki/Category:IDEF" class="extiw external" title="commons:Category:IDEF">IDEF</a></span>.</div></div>

</div>

<ul><li><a rel="nofollow" class="external text" href="http://www.idef.com">Integrated DEFinition Methods</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20070622145629/https://idbms.navo.navy.mil/DataModel/IDEF1X.html">Data Modeling</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20070126094915/http://www.stsc.hill.af.mil/crosstalk/1995/06/IDEF.asp">The IDEF Process Modeling Methodology</a> by Robert P. Hanrahan 1995</li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Software_engineering336" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Software_engineering336" style="font-size:114%;margin:0 4em"><a href="Software_engineering" title="Software engineering">Software engineering</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Fields</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Computer_programming" title="Computer programming">Computer programming</a></li>

<li><a href="DevOps" title="DevOps">DevOps</a></li>

<li><a href="Empirical_software_engineering" title="Empirical software engineering">Empirical software engineering</a></li>

<li><a href="Experimental_software_engineering" title="Experimental software engineering">Experimental software engineering</a></li>

<li><a href="Formal_methods" title="Formal methods">Formal methods</a></li>

<li><a href="Requirements_engineering" title="Requirements engineering">Requirements engineering</a></li>

<li><a href="Search-based_software_engineering" title="Search-based software engineering">Search-based software engineering</a></li>

<li><a href="Site_reliability_engineering" title="Site reliability engineering">Site reliability engineering</a></li>

<li><a href="Social_software_engineering" title="Social software engineering">Social software engineering</a></li>

<li><a href="Software_deployment" title="Software deployment">Software deployment</a></li>

<li><a href="Software_design" title="Software design">Software design</a></li>

<li><a href="Software_maintenance" title="Software maintenance">Software maintenance</a></li>

<li><a href="Software_testing" title="Software testing">Software testing</a></li>

<li><a href="Systems_analysis" title="Systems analysis">Systems analysis</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concepts</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Abstraction_(computer_science)" title="Abstraction (computer science)">Abstraction</a></li>

<li><a href="Computer_compatibility" title="Computer compatibility">Compatibility</a>

<ul><li><a href="Backward_compatibility" title="Backward compatibility">Backward compatibility</a></li>

<li><a href="Compatibility_layer" title="Compatibility layer">Compatibility layer</a></li>

<li><a href="Compatibility_mode" title="Compatibility mode">Compatibility mode</a></li>

<li><a href="Forward_compatibility" title="Forward compatibility">Forward compatibility</a></li>

<li><a href="Software_incompatibility" title="Software incompatibility">Software incompatibility</a></li></ul></li>

<li><a href="Component-based_software_engineering" title="Component-based software engineering">Component-based software engineering</a></li>

<li><a href="Data_modeling" title="Data modeling">Data modeling</a></li>

<li><a href="Enterprise_architecture" title="Enterprise architecture">Enterprise architecture</a></li>

<li><a href="Functional_specification" title="Functional specification">Functional specification</a></li>

<li><a href="Modeling_language" title="Modeling language">Modeling language</a></li>

<li><a href="Programming_paradigm" title="Programming paradigm">Programming paradigm</a></li>

<li><a href="Software" title="Software">Software</a></li>

<li><a href="Software_archaeology" title="Software archaeology">Software archaeology</a></li>

<li><a href="Software_architecture" title="Software architecture">Software architecture</a></li>

<li><a href="Software_configuration_management" title="Software configuration management">Software configuration management</a></li>

<li><a href="Software_development_process" title="Software development process">Software development process/methodology</a></li>

<li><a href="Software_quality" title="Software quality">Software quality</a></li>

<li><a href="Software_quality_assurance" title="Software quality assurance">Software quality assurance</a></li>

<li><a href="Software_system" title="Software system">Software system</a></li>

<li><a href="Software_verification_and_validation" title="Software verification and validation">Software verification and validation</a></li>

<li><a href="Structured_analysis" title="Structured analysis">Structured analysis</a>

<ul><li><a href="Essential_systems_analysis" title="Essential systems analysis">Essential analysis</a></li></ul></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Orientations</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Agile_software_development" title="Agile software development">Agile</a></li>

<li><a href="Aspect-oriented_programming" title="Aspect-oriented programming">Aspect-oriented</a></li>

<li><a href="Object-oriented_programming" title="Object-oriented programming">Object orientation</a></li>

<li><a href="Ontology_(information_science)" title="Ontology (information science)">Ontology</a></li>

<li><a href="Service-oriented_architecture" title="Service-oriented architecture">Service orientation</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Models</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Developmental</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Agile_software_development" title="Agile software development">Agile</a></li>

<li><a href="Executable_UML" title="Executable UML">Executable UML</a></li>

<li><a href="Incremental_build_model" title="Incremental build model">Incremental model</a></li>

<li><a href="Iterative_and_incremental_development" title="Iterative and incremental development">Iterative model</a></li>

<li><a href="Software_prototyping" title="Software prototyping">Prototype model</a></li>

<li><a href="Scrum_(software_development)" title="Scrum (software development)">Scrum</a></li>

<li><a href="Spiral_model" title="Spiral model">Spiral model</a></li>

<li><a href="V-model_(software_development)" title="V-model (software development)">V-model</a></li>

<li><a href="Waterfall_model" title="Waterfall model">Waterfall model</a></li>

<li><a href="Model-driven_engineering" title="Model-driven engineering">Model-driven engineering</a></li>

<li><a href="Round-trip_engineering" title="Round-trip engineering">Round-trip engineering</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Other</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Data_model" title="Data model">Data model</a></li>

<li><a href="Entity%E2%80%93relationship_model" title="Entity–relationship model">ER model</a></li>

<li><a href="Function_model" title="Function model">Function model</a></li>

<li><a href="Information_model" title="Information model">Information model</a></li>

<li><a href="Metamodeling" title="Metamodeling">Metamodeling</a></li>

<li><a href="Object_model" title="Object model">Object model</a></li>

<li><a href="ISO/IEC_15504" title="ISO/IEC 15504">SPICE</a></li>

<li><a href="Systems_modeling" title="Systems modeling">Systems model</a></li>

<li><a href="View_model" title="View model">View model</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Languages</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul>

<li><a href="Systems_modeling_language" title="Systems modeling language">SysML</a></li>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Systems_design" title="Systems design">Systems design</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Software_requirements_specification" title="Software requirements specification"> Requirements</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Functional_requirement" title="Functional requirement">Functional requirement</a></li>

<li><a href="Non-functional_requirement" title="Non-functional requirement">Non-functional requirement</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Capacity_planning" title="Capacity planning"> Capacity</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Active_users" title="Active users"> Users</a></li>

<li><a href="Central_processing_units" class="mw-redirect" title="Central processing units"> Compute</a></li>

<li><a href="Computer_memory" title="Computer memory"> Memory</a></li>

<li><a href="Computer_data_storage" title="Computer data storage"> Storage</a></li>

<li><a href="Bandwidth_(computing)" title="Bandwidth (computing)"> Network</a></li>

<li><a href="Web_traffic" title="Web traffic">Web traffic</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Interface_(computing)" title="Interface (computing)"> Interface</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="GraphQL" title="GraphQL">GraphQL</a></li>

<li><a href="Webhook" title="Webhook">Webhook</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="High-level_design" title="High-level design">High-level design</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Client_(computing)" title="Client (computing)"> Client</a></li>

<li><a href="Load_balancing_(computing)" title="Load balancing (computing)"> Load balancing</a></li>

<li><a href="Application_server" title="Application server">Application server</a></li>

<li><a href="Message_queue" title="Message queue">Message queue</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="System_Integration" class="mw-redirect" title="System Integration"> Integration</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Vertical_integration" title="Vertical integration"> Vertical</a></li>

<li><a href="API_management" title="API management"> API Gateway</a></li>

<li><a href="Event_store" title="Event store"> Event Source</a></li>

<li><a href="Batch_processing" title="Batch processing"> Batch</a></li>

<li><a href="Stream_processing" title="Stream processing">Stream</a></li>

<li><a href="Orchestration_(computing)" title="Orchestration (computing)"> Orchestration</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Architectures" class="mw-redirect" title="Architectures">Architectures</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Monolithic_application" title="Monolithic application"> Monolithic</a></li>

<li><a href="Microservices" title="Microservices">Microservices</a></li>

<li><a href="Event-driven_architecture" title="Event-driven architecture"> Event-Driven</a></li>

<li><a href="Client%E2%80%93server_model" title="Client–server model"> Client–server</a></li>

<li><a href="Serverless_computing" title="Serverless computing"> Serverless</a></li>

<li><a href="Circuit_breaker_design_pattern" title="Circuit breaker design pattern"> Circuit breaker</a></li>

<li><a href="Rate_limiting" title="Rate limiting">Rate limiting</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Database" title="Database">Database</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Relational_database" title="Relational database"> Relational</a></li>

<li><a href="NoSQL" title="NoSQL">NoSQL</a></li>

<li><a href="Graph_database" title="Graph database"> Graph</a></li>

<li><a href="Key%E2%80%93value_database" title="Key–value database"> Key–value</a></li>

<li><a href="Time_series_database" title="Time series database"> Time series</a></li>

<li><a href="Data_orientation" title="Data orientation"> Column Oriented</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Systems_design" title="Systems design"> Principles</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Consistency_(database_systems)" title="Consistency (database systems)">Consistency</a></li>

<li><a href="Reliability_engineering" title="Reliability engineering">Reliability</a></li>

<li><a href="CAP_theorem" title="CAP theorem">CAP theorem</a></li>

<li><a href="Software_maintenance" title="Software maintenance"> Maintainability</a></li>

<li><a href="Computer_configuration" title="Computer configuration"> Configurability</a></li>

<li><a href="Modularity" title="Modularity">Modularity</a></li>

<li><a href="Durability_(database_systems)" title="Durability (database systems)"> Durability</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Scalability" title="Scalability">Scalability</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Service_statelessness_principle" title="Service statelessness principle"> Stateless</a></li>

<li><a href="Asynchronous_I/O" title="Asynchronous I/O">Asynchronous I/O</a></li>

<li><a href="Loose_coupling" title="Loose coupling">Loose coupling</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Availability" title="Availability">Availability</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Fault_tolerance" title="Fault tolerance">Fault tolerance</a></li>

<li><a href="Failover" title="Failover">Failover</a></li>

<li><a href="Single_point_of_failure" title="Single point of failure">Single point of failure</a></li>

<li><a href="Replication_(computing)" title="Replication (computing)"> Replication</a></li>

<li><a href="Consistent_hashing" title="Consistent hashing">Consistent hashing</a></li>

<li><a href="Circuit_breaker_design_pattern" title="Circuit breaker design pattern"> Circuit breaker</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Latency_(engineering)" title="Latency (engineering)">Latency</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Cache_(computing)" title="Cache (computing)"> Cache</a></li>

<li><a href="Shard_(database_architecture)" title="Shard (database architecture)"> Shard </a></li>

<li><a href="Database_index" title="Database index">Database index</a></li>

<li><a href="Cache_prefetching" title="Cache prefetching"> Pre-caching</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Computer_data_storage" title="Computer data storage"> Storage</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Object_storage" title="Object storage">Object storage</a></li>

<li><a href="Block-level_storage" title="Block-level storage"> Block storage</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;"><a href="Observability_(software)" title="Observability (software)"> Observability</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Logging_(computing)" title="Logging (computing)"> Logging</a></li>

<li><a href="Software_metric" title="Software metric"> Metrics</a></li>

<li><a href="Tracing_(software)" title="Tracing (software)"> Tracing </a></li>

<li><a href="Failure_rate" title="Failure rate"> Error rate </a></li>

<li><a href="Queries_per_second" title="Queries per second">Queries per second </a></li>

<li><a href="Notification_system" title="Notification system">Notification system</a></li>

<li><a href="Anomaly_detection" title="Anomaly detection">Anomaly detection</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related fields</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Computer_engineering" title="Computer engineering">Computer engineering</a></li>

<li><a href="Computer_science" title="Computer science">Computer science</a></li>

<li><a href="Information_science" title="Information science">Information science</a></li>

<li><a href="Project_management" title="Project management">Project management</a></li>

<li><a href="Risk_management" title="Risk management">Risk management</a></li>

<li><a href="Systems_engineering" title="Systems engineering">Systems engineering</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2" style="font-weight:bold;"><div>

<ul><li><span class="noviewer" typeof="mw:File"><span title="Category"></span></span> Category</li>

<li><span class="noviewer" typeof="mw:File"><span title="Commons page"></span></span> <a href="https://commons.wikimedia.org/wiki/Category:Software_engineering" class="extiw external" title="commons:Category:Software engineering">Commons</a></li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-12-03" href="https://en.wikipedia.org/wiki/?title=IDEF&oldid=1260944312">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>